ℹ️ Issue

Closes https://vidushimisra.atlassian.net/browse/SSF-108

📝 Description

1. I refactored the frontend and backend request types/entities to now have a list of Orders a single request is associated with as opposed to just one. This accurately reflects the many to one relationship with multiple orders being able to fulfill a request
2. I added a route to get all associated order details from a request. This will be necessary for the new request management page and viewing details of that request.

In terms of code changes it was mainly defining the new backend route and writing tests for that. The backend route I added is:
@get('/get-all-order-details/:requestId'). I also had to do some refactoring to transition from one associated order to a list of them.

Also, right now the request management page is outdated. For one, it is still associating one order with one request and for another, request management and order management is now being split into to pages. I had to refactor this outdated page for the updated request type and I chose to simply use the first order in the orders list (orders[0]) and have everything else be the same. Thus, this page does not work as intended but it can still be loaded. This change is just a placeholder for now, the new design pages will take over. The associated route is: request-form/:pantryId

✔️ Verification

I used swagger to verify my backend route worked as expected and I wrote some jest tests to ensure this. I added controller and service tests for the @get('/get-all-order-details/:requestId') route.

🏕️ (Optional) Future Work / Notes

The request form frontend is outdated and my refactoring of it to account for the orders list is just a placeholder. This will be overwritten in the future.